[release-4.19] OCPBUGS-80412: Bump google.golang.org/grpc to v1.79.3 by ocp-sustaining-admins · Pull Request #76 · openshift/cluster-api-operator

ocp-sustaining-admins · 2026-05-01T16:22:38Z

This is an automated PR from the ARC system.

Go version used: go1.23.12

Patch applied: github.com/openshift-sustaining/grpc-go@v1.75.1-sec.1

Modules affected: ., hack/chart-update, test

The commands used to generate this PR were:

go mod edit -replace google.golang.org/grpc=github.com/openshift-sustaining/grpc-go@v1.75.1-sec.1
go mod tidy
go mod vendor

Note: This package bump updated the go directive in go.mod. This may cause CI check failures if the repository's CI configuration does not yet support the updated Go version.

A member of the Red Hat Openshift Sustaining Team will review the PR and take appropriate action.

openshift-ci-robot · 2026-05-01T16:22:45Z

@ocp-sustaining-admins: This pull request references Jira Issue OCPBUGS-80412, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-80412 to depend on a bug targeting a version in 4.20.0, 4.20.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated PR from the ARC system.

Go version used: go1.23.12

Patch applied: github.com/openshift-sustaining/grpc-go@v1.75.1-sec.1

Modules affected: ., hack/chart-update, test

The commands used to generate this PR were:
go mod edit -replace google.golang.org/grpc=github.com/openshift-sustaining/grpc-go@v1.75.1-sec.1
go mod tidy
go mod vendor
Note: This package bump updated the go directive in go.mod. This may cause CI check failures if the repository's CI configuration does not yet support the updated Go version.

A member of the Red Hat Openshift Sustaining Team will review the PR and take appropriate action.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

coderabbitai · 2026-05-01T16:22:47Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: d563b160-2735-4466-9888-ad1aa35f6b0e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

openshift-ci · 2026-05-01T16:23:22Z

Hi @ocp-sustaining-admins. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

shannon · 2026-05-01T16:59:32Z

/ok-to-test

rh-soboh · 2026-05-08T17:55:18Z

/jira refresh

openshift-ci-robot · 2026-05-08T17:55:23Z

@rh-soboh: This pull request references Jira Issue OCPBUGS-80412, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

rh-soboh · 2026-05-08T17:56:03Z

/jira refresh

openshift-ci-robot · 2026-05-08T17:56:41Z

@rh-soboh: This pull request references Jira Issue OCPBUGS-80412, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.19.z) matches configured target version for branch (4.19.z)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-80588 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-80588 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.z
bug has dependents

Requesting review from QA contact:
/cc @rissh

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

rh-soboh · 2026-05-09T04:48:14Z

/test e2e-aws-ovn-techpreview

openshift-ci · 2026-05-09T07:37:15Z

@ocp-sustaining-admins: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

damdo

/label backport-risk-assessed

/approve

/lgtm

/verified by ci

openshift-ci · 2026-05-13T10:34:06Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damdo, ocp-sustaining-admins

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~OWNERS~~ [damdo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

damdo · 2026-05-18T08:55:52Z

/verified by ci

openshift-ci-robot · 2026-05-18T08:56:06Z

@damdo: This PR has been marked as verified by ci.

Details

In response to this:

/verified by ci

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2026-05-18T09:00:07Z

@ocp-sustaining-admins: Jira Issue Verification Checks: Jira Issue OCPBUGS-80412
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-80412 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

This is an automated PR from the ARC system.

Go version used: go1.23.12

Patch applied: github.com/openshift-sustaining/grpc-go@v1.75.1-sec.1

Modules affected: ., hack/chart-update, test

The commands used to generate this PR were:
go mod edit -replace google.golang.org/grpc=github.com/openshift-sustaining/grpc-go@v1.75.1-sec.1
go mod tidy
go mod vendor
Note: This package bump updated the go directive in go.mod. This may cause CI check failures if the repository's CI configuration does not yet support the updated Go version.

A member of the Red Hat Openshift Sustaining Team will review the PR and take appropriate action.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 1, 2026

openshift-ci Bot requested review from RadekManak and mzazrivec May 1, 2026 16:23

openshift-ci Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 1, 2026

rh-soboh force-pushed the release-4.19_CVE-2026-33186 branch from 6c956c5 to 262243d Compare May 4, 2026 13:54

rh-soboh added 2 commits May 8, 2026 18:47

UPSTREAM: <drop>: OCPBUGS-80412: Bump google.golang.org/grpc to v1.79.3

6c9b390

UPSTREAM: 1013: OCPBUGS-80412: Bump google.golang.org/grpc to v1.79.3

d57c107

rh-soboh force-pushed the release-4.19_CVE-2026-33186 branch from 262243d to d57c107 Compare May 8, 2026 17:48

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 8, 2026

openshift-ci Bot requested a review from rissh May 8, 2026 17:56

damdo reviewed May 13, 2026

View reviewed changes

openshift-ci Bot assigned damdo May 13, 2026

openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels May 13, 2026

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 13, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label May 18, 2026

openshift-merge-bot Bot merged commit 21f8583 into openshift:release-4.19 May 18, 2026
9 checks passed

damdo mentioned this pull request May 18, 2026

/verified command not picked up from PR review comments openshift-eng/jira-lifecycle-plugin#176

Open

Conversation

ocp-sustaining-admins commented May 1, 2026

Uh oh!

openshift-ci-robot commented May 1, 2026

Uh oh!

coderabbitai Bot commented May 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

openshift-ci Bot commented May 1, 2026

Uh oh!

shannon commented May 1, 2026

Uh oh!

rh-soboh commented May 8, 2026

Uh oh!

openshift-ci-robot commented May 8, 2026

Uh oh!

rh-soboh commented May 8, 2026

Uh oh!

openshift-ci-robot commented May 8, 2026

Uh oh!

rh-soboh commented May 9, 2026

Uh oh!

openshift-ci Bot commented May 9, 2026

Uh oh!

damdo left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-ci Bot commented May 13, 2026

Uh oh!

damdo commented May 18, 2026

Uh oh!

openshift-ci-robot commented May 18, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented May 18, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

coderabbitai Bot commented May 1, 2026 •

edited

Loading